``\emph{Quality is a team issue. The most diligent developer placed on a team that just doesn't care will find it difficult to maintain the enthusiasm needed to fix niggling problems.}" \cite{PragmProg}

The development of iSquirrel was a full combination of the following:

\begin{itemize}
\item team effort
\item team excitement
\item team communication.
\end{itemize}

The team accommodated the Scrum development method with a slight hint of Extreme Programming (XP). We had 2-3 stand-up meetings per week where each team member stated their progress and difficulties with their current task thus making sure that all members did keep up with the project's velocity. A sprint planning meeting was being held at the beginning of each iteration where more requirements were defined, the goals of the iteration were decided and the software design models were specified or re-factored. At the end of each iteration the team performed integration and regression testing of the system as well as code reviews. Coding was mostly done in pairs.

Our project was hosted on Google Code\footnote{Google Code Project Hosting: \url{http://www.code.google.com}} as an open source project under the MIT Licence where everyone could track the project progress and status. Google Code Project Hosting comes with Subversion and provided us with a simple bug reporting interface and a wiki where the documentation was composed. The main development was done in the trunk and each new feature was developed in separate branches. Tagging was done at the end of each iteration, after integration and testing was completed. Unit tests and regression testing were performed in all of the development phases. Testing was also performed by various users to measure the performance, accuracy and usability of the system.